<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Troubleshooting monitoring | ElasticSearch 7.7 权威指南中文版</title>
	<meta name="keywords" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <meta name="description" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
	<link rel="stylesheet" type="text/css" href="../static/styles.css" />
	<script>
	var _link = 'monitoring-troubleshooting.html';
    </script>
</head>
<body>
<div class="main-container">
    <section id="content">
        <div class="content-wrapper">
            <section id="guide" lang="zh_cn">
                <div class="container">
                    <div class="row">
                        <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                            <div style="color:gray; word-break: break-all; font-size:12px;">原英文版地址: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/monitoring-troubleshooting.html" rel="nofollow" target="_blank">https://www.elastic.co/guide/en/elasticsearch/reference/7.7/monitoring-troubleshooting.html</a>, 原文档版权归 www.elastic.co 所有<br/>本地英文版地址: <a href="../en/monitoring-troubleshooting.html" rel="nofollow" target="_blank">../en/monitoring-troubleshooting.html</a></div>
                        <!-- start body -->
                  <div class="page_header">
<strong>重要</strong>: 此版本不会发布额外的bug修复或文档更新。最新信息请参考 <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html" rel="nofollow">当前版本文档</a>。
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="monitor-elasticsearch-cluster.html">Monitor a cluster</a></span>
»
<span class="breadcrumb-node">Troubleshooting monitoring</span>
</div>
<div class="navheader">
<span class="prev">
<a href="pause-export.html">« Pausing data collection</a>
</span>
<span class="next">
<a href="frozen-indices.html">Frozen indices »</a>
</span>
</div>
<div class="chapter">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="monitoring-troubleshooting"></a>Troubleshooting monitoring<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/monitoring/troubleshooting.asciidoc">edit</a>
</h2>
</div></div></div>

<p>Use the information in this section to troubleshoot common problems and find
answers for frequently asked questions. See also
<a href="https://www.elastic.co/guide/en/logstash/7.7/monitoring-troubleshooting.html" class="ulink" target="_top">Troubleshooting monitoring in Logstash</a>.</p>
<p>For issues that you cannot fix yourself … we’re here to help.
If you are an existing Elastic customer with a support contract, please create
a ticket in the
<a href="https://support.elastic.co/customers/s/login/" class="ulink" target="_top">Elastic Support portal</a>.
Or post in the <a href="https://discuss.elastic.co/" class="ulink" target="_top">Elastic forum</a>.</p>
<h3>
<a id="monitoring-troubleshooting-no-data"></a>No monitoring data is visible in Kibana<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/monitoring/troubleshooting.asciidoc">edit</a>
</h3>
<p><span class="strong strong"><strong>Symptoms</strong></span>:
There is no information about your cluster on the <span class="strong strong"><strong>Stack Monitoring</strong></span> page in
Kibana.</p>
<p><span class="strong strong"><strong>Resolution</strong></span>:
Check whether the appropriate indices exist on the monitoring cluster. For
example, use the <a class="xref" href="cat-indices.html" title="cat indices API">cat indices</a> command to verify that
there is a <code class="literal">.monitoring-kibana*</code> index for your Kibana monitoring data and a
<code class="literal">.monitoring-es*</code> index for your Elasticsearch monitoring data. If you are collecting
monitoring data by using Metricbeat the indices have <code class="literal">-mb</code> in their names. If
the indices do not exist, review your configuration. For example, see
<a class="xref" href="monitoring-production.html" title="Monitoring in a production environment"><em>Monitoring in a production environment</em></a>.</p>
<h3>
<a id="monitoring-troubleshooting-uuid"></a>Monitoring data for some Elastic Stack nodes or instances is missing from Kibana<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/monitoring/troubleshooting.asciidoc">edit</a>
</h3>
<p><span class="strong strong"><strong>Symptoms</strong></span>:
The <span class="strong strong"><strong>Stack Monitoring</strong></span> page in Kibana does not show information for some nodes or
instances in your cluster.</p>
<p><span class="strong strong"><strong>Resolution</strong></span>:
Verify that the missing items have unique UUIDs. Each Elasticsearch node, Logstash node,
Kibana instance, Beat instance, and APM Server is considered unique based on its
persistent UUID, which is found in its <code class="literal">path.data</code> directory. Alternatively, you
can find the UUIDs in the product logs at startup.</p>
<p>In some cases, you can also retrieve this information via APIs:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
For Beat instances, use the HTTP endpoint to retrieve the <code class="literal">uuid</code> property.
For example, refer to
<a href="https://www.elastic.co/guide/en/beats/filebeat/7.7/http-endpoint.html" class="ulink" target="_top">Configure an HTTP endpoint for Filebeat metrics</a>.
</li>
<li class="listitem">
For Kibana instances, use the
<a href="https://www.elastic.co/guide/en/kibana/7.7/access.html#status" class="ulink" target="_top">status endpoint</a> to retrieve the <code class="literal">uuid</code> property.
</li>
<li class="listitem">
For Logstash nodes, use the
<a href="https://www.elastic.co/guide/en/logstash/7.7/monitoring-logstash.html" class="ulink" target="_top">monitoring APIs root resource</a> to
retrieve the <code class="literal">id</code> property.
</li>
</ul>
</div>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>When you install Elasticsearch, Logstash, Kibana, APM Server, or Beats, their <code class="literal">path.data</code>
directory should be non-existent or empty; do not copy this directory from other
installations.</p>
</div>
</div>
</div>
<div class="navfooter">
<span class="prev">
<a href="pause-export.html">« Pausing data collection</a>
</span>
<span class="next">
<a href="frozen-indices.html">Frozen indices »</a>
</span>
</div>
</div>

                  <!-- end body -->
                        </div>
                        <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                        
                        </div>
                    </div>
                </div>
            </section>
        </div>
    </section>
</div>
<script src="../static/cn.js"></script>
</body>
</html>